>FW_CDropCommand::PrivHandleDrop calls DoDrop in a loop and assigns the
>result of DoDrop to a local variable. However, the result of each iteration
>of DoDrop zaps the result of the previous iteration. Therefore, the result
>of PrivHandleDrop is the success/failure state of the last dropped object.
>
>This looks like a bug, does it?
I don't think it's a bug... The iteration stops if the result of DoDrop is false. So PrivHandleDrop returns true only if all the objects were dropped successfully.